Fix contextId handling in workload-orchestration target commands

Summary

This PR addresses critical issues with contextId parameter handling in the workload-orchestration extension's target create and update commands, ensuring proper Azure resource management workflows.

Changes Made

1. Added required context-id parameter to target create command

• Added --context-id parameter as a required argument for target creation
• Ensures all targets are properly associated with their execution context
• Prevents creation of orphaned target resources

2. Fixed target update command contextId preservation

• Problem: The target update command was failing with ObjectMissingRequiredProperty: contextId errors
• Root Cause: The AAZ update operation follows a READ → PATCH → PUT pattern, but the contextId property was being dropped from the PUT payload due to missing schema definition
• Solution: Added contextId property to the target schema in _UpdateHelper._build_schema_target_read() method
• Impact: Target update operations now properly preserve the contextId during round-trip operations

Technical Details

• Modified _update.py to include contextId in the target resource schema
• Added proper serialization mapping (serialized_name="contextId")
• Marked as required field (flags={"required": True})
• Ensures compatibility with Azure Resource Manager requirements

Testing

• Verified target update commands no longer fail with contextId validation errors
• Confirmed contextId is preserved during update operations
• Tested with various target properties to ensure no regression

Test Evidence.pdf

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.